Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1636

reference
376-tree-1
name
1636
tree-preservation-order

undefined

376-tpo-1
uprn
address-text
point
POINT (-1.030185 50.884564)
geometry
MULTIPOLYGON (((-1.030128 50.884558,-1.030130 50.884569,-1.030138 50.884579,-1.030151 50.884587,-1.030166 50.884593,-1.030184 50.884594,-1.030201 50.884593,-1.030217 50.884588,-1.030230 50.884580,-1.030238 50.884570,-1.030241 50.884559,-1.030239 50.884548,-1.030231 50.884538,-1.030219 50.884530,-1.030203 50.884524,-1.030185 50.884523,-1.030168 50.884524,-1.030152 50.884529,-1.030139 50.884537,-1.030131 50.884547,-1.030128 50.884558)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL